Virtual reality device with varying interactive modes for document viewing and editing

ABSTRACT

A virtual reality device can implement varying interactive modes for document viewing and editing by displaying, at an application container level, a current mode view in a view frame of the virtual reality device; and in response to receiving an overview command trigger, determining context, including that the current mode view is at the application container level; expanding to a next level view of, e.g., a task level or an overview level; and displaying, at a next level, the next level view in the view frame of the virtual reality device. The current mode view of the application container level includes a container space of an application and an application container level rule for the container space. Conversely, the virtual reality device can adjust the next level view back to the application container level in response to a focused command trigger and identified region of interest.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/640,537, filed Mar. 8, 2018.

BACKGROUND

Virtual reality and the various levels of immersion into a virtualenvironment, including augmented and mixed reality scenarios, are beingimplemented for numerous applications, including medical or militarytraining, games, and travel exploration. Increasing attention is beingmade to productivity applications to enable users to engage in officework.

Virtual reality refers to a fully immersive, computer-generatedexperience. For example, a user can put on a headset, and everything inthe user's field of view is a pixel. In comparison, augmented realityand mixed reality include experiences in which reality is supplementedwith additional information such as available on a heads-up display,overlay, or on a mobile device. Augmented reality and mixed reality aresimilar, but mixed reality takes augmented reality one step further sothat not only is the real world and the digitally represented worldavailable, the digitally represented objects interact with thereal-world element. For example, holograms can be rendered in the realworld and appear to interact with objects in the physical world.

BRIEF SUMMARY

Virtual reality (VR) devices with multiple viewing modes to accommodatea user's work context are described.

A VR device can implement varying interactive modes for document viewingand editing. A VR device can display a current mode view in a view frameof the virtual reality device, the current mode view comprising acurrent mode rule for a container space (e.g., when certainapplications, if any, are put to sleep to minimize power consumption),wherein the container space comprises an application container of anapplication. Then, in response to receiving an overview command trigger,the VR device can determine context including a current container level.When the current container level can expand at least one level, the VRdevice expands to a next mode view, wherein the next mode view is a nextexpanded container level and applies a next mode rule for the containerspace. In response to receiving a focus command trigger and identifyinga region of interest, the VR device can adjust the view frame to theregion of interest, display a focused mode view, and apply a focusedmode rule for the container space.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B illustrate example VR scenarios for applications inwhich implementations of the described varying interactive modes can beapplied.

FIGS. 2A and 2B illustrate example application container level, tasklevel, and overview level configurations for document viewing andediting.

FIGS. 3A and 3B illustrate example processes for varying interactivemodes for a VR device.

FIGS. 4A-4D illustrate example processes for moving between interactivemodes having application container level, task level, and overview levelconfigurations for document viewing and editing.

FIGS. 5A-5I illustrate an example scenario of using a VR device withvarying interactive modes for document viewing and editing.

FIG. 6 illustrates an example computing system of a VR device.

FIGS. 7A-7C illustrate example head-mounted display-based VR devicesthat may be used in certain implementations described herein.

DETAILED DESCRIPTION

Virtual reality (VR) devices with multiple viewing modes to accommodatea user's work context are described. VR devices such as VR headsets,holographic-enabled headsets, and other head mounted displays can beused to implement virtual reality, mixed reality, and augmented realityapplications, including productivity applications. In someimplementations, the described VR devices and techniques can enable auser to perform difficult productivity tasks using a portable wirelessdevice and VR headset.

One challenge for using a VR device to engage in information work usinga typical office paradigm with multiple monitors and windows is theavailable resolution for viewing and interacting with text. Indeed, textquality can suffer due to lenses that spread a display over a wide fieldof view. In addition, gestural and eye tracking inputs may not providethe accuracy and high-speed input expected when inputting and editingtext. productivity tasks such as spreadsheet editing can require finecontrol of mapping gestures to actions and a high-resolution image toview the content of the cells of the spreadsheet.

The described techniques and systems are applicable for supportinginteraction with multiple applications and objects in a virtual realityenvironment. The applications may be media applications (e.g., videos,television, movies), gaming applications, and productivity applications.Productivity applications include content creation and contentconsumption applications including, but not limited to, word processingapplications, spreadsheet applications, presentation applications,note-taking application, whiteboard applications, email or messagingapplications, drawing applications, web browser applications, search andresearch applications, and reader applications.

The described VR devices and techniques use work context, controls andhead movement tracking to support intense document creation. In somecases, the described VR devices and techniques support the integrationof keyboard and mouse (or touchpad/trackpad) interactions. In somecases, such as when using devices that support mixed realityapplications, both the keyboard (with user hands) and the virtualdisplay can be viewed by the user.

The described techniques support switching between documents (andapplications), as well as being able to get an overview of all documentsthat are open, looking around, and then focusing back on a specifictask. The described techniques maintain the expected spatialrelationships for the user so that the user does not lose track of wherethings are in the environment around them.

An activation trigger for switching modes can include a combination ofattention and selection. For example, head tracking (‘attention’) and akeyboard, mouse, controller, voice, or gestural command (‘selection’)can be used to enter a focused mode. For both a focused mode and anoverview mode, the modes can be initiated by a command selection (e.g.,from a menu or icon), which may be verbal, gestural, touch, a selectionof one or more keys of a keyboard, or mouse button. In some cases, theactivation can be triggered automatically based on, for example,detecting high priority changes at a different level of activity.

FIGS. 1A and 1B illustrate example VR scenarios for applications inwhich implementations of the described varying interactive modes can beapplied. Referring to FIG. 1A, a user 100 can be working with one ormore applications in a virtual reality environment 110. The content ofthe virtual reality environment 110 that a user is able to see in frontof them can be referred to as a “view frame”—the boundary of thedisplay. Since a virtual reality environment 110 may effectivelysurround the user 100, the view frame is considered the area of theenvironment that the user can see at a given time. The user 100 can beinteracting with the one or more applications to, for example, consumeor create content, or communicate with others. In this example, thevirtual reality environment has four documents 112, 114, 116, and 118,where the document 118 includes slides 120. In the virtual realityenvironment 110 the system maintains spatial relationships between thedocuments so that the user 100 knows that, for example, the slides 120are on the right and other documents 112, 114, and 116 can be viewed asthe user 100 turns their head to the left (or selects an arrow to movethe view to the left or selects some other user interface element oruses an input device element like an arrow key of a controller orkeyboard).

Referring to FIG. 1B, as mentioned above, performing complexproductivity tasks such as spreadsheet editing can require ahigh-resolution experience in a virtual reality environment. Here, theuser 100 can activate an interactive mode corresponding to a focusedmode such that a spreadsheet 132 can be provided with appropriateresolution in a view frame 135. Then, the user 100 can interact with thecells 140 with better user interaction performance and improved userefficiency. For example, the improved text display can improve userefficiency and improve user interaction performance with the smallelements. The different interactive modes may enable a user to movebetween an application container level, a task level, and an overviewlevel while maintaining the spatial relationships between documents orother objects in the virtual reality environment.

FIGS. 2A and 2B illustrate example application container level, tasklevel, and overview level configurations for document viewing andediting. Referring to FIG. 2A, a virtual reality environment 200 caninclude a plurality of application containers (e.g., 210). Eachapplication container provides a space in which appropriate graphics canbe rendered for an application. An application container can beconsidered to operate within an application container space 220. Theapplication container space 220 provides an area, or interface, forinteraction with the application. In some cases, multiple applicationcontainer elements 222 can be provided within the application containerspace 220. The application container space 220 can thus include one ormore application container elements 222 that can support graphics forthe same application (and/or document). For example, the document 118 inFIG. 1A can include the multiple slides 120 arranged in the applicationcontainer space for that document 118. Each of the slides 120 operate inan application container element.

When the current mode is an application container level mode, a user canhave a current mode view of an application container level view with theview frame on the application container space 220 (and which a user mayfix within the view frame or permit change of view to anotherapplication container space in the virtual reality environment). This isshown in FIG. 1B, where the user 100 has an application container spacewith the spreadsheet 132 in the view frame 135.

The current mode view of the application container level view (e.g.,where the application container space is expanded in the view frame) caninclude a current mode rule for the container space of operating theapplication within the application container space and stoppingoperation of any applications in spaces not in the view frame (e.g., theother applications, not visible, “sleep”).

In some cases, more than one application or more than one document isbeneficial for performing a particular task. Accordingly, certainapplication containers, each operating within their correspondingapplication container space, can be grouped and assigned as a task level230. The current mode view of the task level view (e.g., where there areat least two application container spaces of the same or differentapplications) can include a current mode rule for the container space ofoperating the corresponding application within each of the at least twoapplication container spaces and stopping operation of any applicationsin spaces not in the view frame determined based on head motion (e.g.,the other applications “sleep”).

As described herein, in addition to having a focused mode and supportingthe spatial relationships between application containers, an overviewlevel is provided. Referring to FIG. 2B, the overview level generates anoverview space 240 that provides a view of all application containerspaces 220 in the view area. The overview level can further includeoverview mode rules, such as replacing active elements or event contentdense graphics within an application container space 220 withrepresentations (e.g., application container representations 242). Forexample, operations of any applications within the application containerspaces can be reduced or stopped, which can reduce power consumption.Reduce power consumption may be achieved, in part, due to reducedprocessor load for running the applications. Thus, even when all windowsare in the user's field of view, unless the system is in a focused mode(with an application container space or task level space in the field ofview), a reduced resolution video or image can be provided in the activewindow or a thumbnail or representational image can be provided in placeof an active window. Advantageously the commands provide improvedusability of applications, including productivity applications, in theVR environment.

In some cases, thumbnail representations can replace the graphics in theapplication container spaces. Accordingly, the application containersshown in the overview include graphics for an application containerrepresentation. In some cases, the overview space 240 can maintaincertain spatial relationship characteristics between applicationcontainers so that a user can see that a particular applicationcontainer is to the left or right (or above or below or in front or inback of) another application container.

While in the various modes, additional rules may be implemented tocontrol whether or not the user's head movement will affect the viewframe. For example, a head lock command and a world lock command may beprovided. In response to a head lock command, the system can maintainthe view frame regardless of head position of the user; and in responseto a world lock command, the system can maintain the container spacewithin the view frame while permitting head motion tracking within thecontainer space. Conceptually, a virtual object may be locked to areference location in the real-world environment such that the locationof the virtual object remains constant relative to the real-worldenvironment regardless of the position or angle from which it is viewed.When a head lock command is instantiated, a virtual object may be lockedto the position and direction of a user's head such that the location ofthe virtual object in a user's field of view appears fixed regardless ofa direction in which the user faces. Head-locking may be used, forexample, to display persistent user interface icons in the user's fieldof view, such as a mouse graphic. Head-locking can be used as a way toreduce battery consumption as an inertial measurement unit can be turnedoff during the head-lock scenario. In some cases, the head-locking canbe used to help improve visual clarity and enable a user to move to acomfortable position without having the text or graphics move around. Inthe described world lock scenario, the fixed space is the applicationcontainer (or multiple application containers if in a task level view),and the virtual objects can remain constant relative to the environmentof the application container, but the application container is locked toboundary positions of the user's head and orientation.

FIGS. 3A and 3B illustrate example processes for varying interactivemodes for a VR device. Referring to FIG. 3A, a VR device can performprocess 300 for varying interactive modes for document viewing andediting. The VR device can display a current mode view (302). Thecurrent mode view can include the content of a display area and enforcecertain rules (the “current mode rule”) for container spaces such as theapplication containers 210 described with respect to FIGS. 2A and 2B.The system can receive an overview command trigger (304). The overviewcommand trigger can be any suitable activation trigger. For example, theoverview command trigger can be a specific one or more keys on akeyboard, a selection of a command icon from a menu, a verbal command,or a particular gesture. When an overview command trigger is received,the system can determine context including the current container level(306). The context can further include, but is not limited to, thecontent in the view space, the applications running in the environment,and the corresponding application states for each of those applications.A determination can be made, using the current container levelinformation, whether expansion is available (308). If there is no nextlevel available, no expansion action is taken (310). If there is a nextlevel available, the system will expand to a next mode view (312); andwill apply a next mode rule for the container space (314).

In some cases, there are two modes: a regular operating mode and theoverview mode. The regular operating mode may be the virtual realityenvironment such as illustrated in FIG. 1A or the virtual realityenvironment such as illustrated in FIG. 1B. Thus, in response toreceiving the overview command trigger, if the system is in a regularoperating mode, the system will then move to the overview mode view butif the system is already in the overview mode, no action is taken. Insome cases, there are more than two modes. For example, in theillustrative implementation described herein, there are three modesavailable: one for application container level, one for task level, andone for the overview level. In some cases, the overview command triggerautomatically moves the current mode view to the overview mode viewregardless of what level view is the current mode view. In some cases,the overview command trigger is used to move sequentially through thelevels.

The system can receive a focus command trigger (316). The focus commandtrigger can include a keyboard, mouse, controller, audio, or gesturalcommand. In addition to the focus command trigger, a region of interestis identified in the display of the next mode view (318). The region ofinterest may be identified by performing head tracking and detectinghead position. In some cases, a mouse or gestural selection may be usedto identify the region of interest. Although the identifying the regionof interest is shown subsequent to receiving the focus command trigger,the processes may be performed in any order and even at the same time.The combination of the focus command trigger and the identified regionof interest (the “attention”) can cause the modes to be switched, forexample, by adjusting a view frame to the region of interest (320);displaying a focus mode view (322); and applying a focus mode rule forthe container space (324).

In the case where there are more than two modes, the focus commandtrigger can automatically move the next mode view (e.g., the overviewmode view or the task mode view for the three-mode implementation) tothe application container level or may move the modes sequentiallythrough the levels.

In more detail, referring to FIG. 3B, a VR device can perform process330 for varying interactive modes for document viewing and editing. TheVR device can display a current mode view (332). The current mode viewcan include the content of a display area and enforce certain rules (the“current mode rule”) for container spaces such as the applicationcontainers 210 described with respect to FIGS. 2A and 2B. The system canreceive a focus command trigger (334). The focus command trigger caninclude a keyboard, mouse, controller, audio, or gestural command. Inaddition to the focus command trigger, a region of interest isidentified in the display of the current mode view (336). The region ofinterest may be identified by performing head tracking and detectinghead position. In some cases, a mouse or gestural selection may be usedto identify the region of interest. Although the identifying the regionof interest is shown subsequent to receiving the focus command trigger,the processes may be performed in any order and even at the same time.

When the focus command trigger is received, the system can determinecontext (e.g., current container level, application, application state,content); and a determination can be made as to whether a focus mode isavailable (338). If there is no focus available, no focus action istaken (340). If there is a focus available, the system will adjust aview frame to the region of interest (342); display a focus mode view(344); and apply a focus mode rule for the container space (346).

As described above, in some cases, there are two modes: a regularoperating mode and the overview mode. The regular operating mode may bethe virtual reality environment such as illustrated in FIG. 1A or thevirtual reality environment such as illustrated in FIG. 1B. Thus, inresponse to receiving the focus command trigger, if the system is in aregular operating mode (where regular operating mode is a focus mode),no action is taken, but if the system is in the overview mode, thesystem will then move to the focused mode view. In some cases, wherethere are more than two modes, the system may automatically move thecurrent mode view to the focused mode view regardless of what level viewis the current mode view or may move the system sequentially through thelevels.

In some cases, when moving from overview level to the task orapplication container level, the focused command trigger can also causethe application (in the application container of interest) to launch.

FIGS. 4A-4D illustrate example processes for moving between interactivemodes having application container level, task level, and overview levelconfigurations for document viewing and editing. Referring to FIG. 4A,in process 400, an application container level view may be displayed ina VR device environment (402). The system can receive an overviewcommand trigger (404); and determine context including current containerlevel (406). Because the current container level is the applicationcontainer level, the system can expand to the task level view (408);display the task level view (410); and apply a next mode rulecorresponding to rules for the task level view (412).

Referring to FIG. 4B and process 420, a task level view may be displayedin a VR device environment (422). The system can receive an overviewcommand trigger (424); and determine context including current containerlevel (426). Because the current container level is the task level, thesystem can expand to the overview level view (428); display the overviewlevel view (430); and apply a next mode rule corresponding to rules forthe overview level view (432).

Referring to FIG. 4C, in process 440, an overview level view may bedisplayed in a VR device environment (442). The system can receive afocus command trigger (444); and identify a region of interest (446).Because the current container level is the overview level view, thesystem can adjust the view frame to the region of interest (448);display the task level view based on the region of interest (450); andapply a focus mode rule corresponding to rules for the task level view(452).

Referring to FIG. 4D, in process 460, a task level view may be displayedin a VR device environment (462). The system can receive a focus commandtrigger (464); and identify a region of interest (466). Because thecurrent container level is the task level view, the system can adjustthe view frame to the region of interest (468); display the applicationcontainer level view based on the region of interest (470); and apply afocus mode rule corresponding to rules for the application containerlevel view (472).

It should be understood that, in some cases, the task level view may bethe same as an application container level view, for example, where asingle application or document is utilized for a particular task.

FIGS. 5A-5I illustrate an example scenario of using a VR device withvarying interactive modes for document viewing and editing.

Referring to FIG. 5A, a user of a virtual reality device may be carryingout tasks using a plurality of applications, some of which may beproductivity applications. FIG. 5A shows an example of applicationcontainers for the illustrative scenario. Here, one applicationcontainer is for an email application and displays a document of anemail message 502; one application container is for a word processingapplication and displays a document of a docx file 504; one applicationcontainer is for a web browser application and displays a document of apage of a search engine 506; and one application container is for apresentation application and displays a document of a presentation file508. Although the application containers are shown each including adifferent application, multiple application containers can be providedfor a same application, but different documents.

Referring to FIG. 5B, an example of an overview level view is provided.The four application containers in the VR environment are shown in theview frame 510A using container representations 512. Here,representation 521 is used for the email message 502, representation 522is used for the content 504, representation 523 is used for the webpage506, and representation 524 is used for the presentation file 508. Insome cases, the representation may be a graphic image to represent thecontent, a thumbnail image of document, or a label (e.g., what the fileis named or some other label or identifier for the underlyingdocument/content). Also shown in the view frame are additionalinteractive elements 530. The additional interactive elements 530 mayinclude command icons or other content.

Referring to FIG. 5C, a user may indicate their selection of a region ofinterest. The system may identify the region of interest based on theuser's head motion and position, or some other input. In the view frame510B, the user has indicated their interest in web browser, and thevirtual reality device can provide a representation of the machine stateindicating that the web browser is the identified region of interest,for example by providing a signal to indicate to a user the identifiedregion of interest. Here, the example of the signal is a highlight 540for the representation 523. In response to receiving both a focuscommand trigger and identifying the region of interest, the system canadjust the view frame to the region of interest. For example, as shownin FIG. 5D, the webpage 506 is provided to the user 550 as anapplication container level view in the view frame 552. While at theapplication container level, the user 550 may navigate in the virtualreality environment to view the other application containers. Forexample, referring to FIG. 5E, a user 550 may turn (554) their head tothe left and change (556) the view frame from the webpage 506 to thedocument 504, such that the application container space for document 504is in the user's view frame 552 as shown in FIG. 5F.

Referring to FIG. 5G, the application container space 560 for the wordprocessing application (e.g., for document 504 of FIG. 5A) can includemultiple container elements as the user is interacting with the workprocessing application in the application container space 560. Forexample, a main window 562 of a word processing application in oneapplication container element and an image 564 that may be inserted isshown in another application container element to one side of the mainwindow 562 application container element. While working within theapplication container space 560, for example, entering content 566 of “Ilove ice cream!”, the user may desire to change their interactive modefrom application container level to a task level 570, which in thisexample includes the application container 572 for the web browserapplication. The processes for changing the interactive mode from themode the user was in for the application container space to the tasklevel mode may be accomplished such as described with respect to process400 of FIG. 4A.

While in the task level 570, the user may interact with the web browserapplication to perform research for their paper on ice cream, forexample, entering a query 574 “ice cream” and performing a search 576,to result in content results 578, as illustrated in FIG. 5H. To reorientherself again on what other tasks may need actions, the user may desireto change the interactive mode to the overview level. The processes forchanging the interactive mode from the mode the user was in for the tasklevel 570 to the overview level may be accomplished such as describedwith respect to process 420 of FIG. 4B, resulting in, for example, theview frame 510C shown in FIG. 5I.

Referring to FIG. 5I, the view frame 510C can include an updatedrepresentation 580 for the document 504 of FIG. 5A, which is updatedwith a label 582 representing the underlying content. The updated labelmay be determined by the system based on the context, for example,identified in operation 426 of process 420 (or as described with respectto operation 306 of FIG. 3A). In some cases, the representation for theapplication container for document 504 may be the same as shown in theview frame 510A as shown in FIG. 5B.

FIG. 6 illustrates an example computing system of a VR device; and FIGS.7A-7C illustrate example head-mounted display-based VR devices that maybe used in certain implementations described herein. The illustrated VRdevices are wearable computing devices. Wearable computing devices withnear-eye displays may also be referred to as “head-mountable displays”,“head-mounted displays,” “head-mounted devices” or “head-mountabledevices.” A head-mountable display places a graphic display or displaysclose to one or both eyes of a wearer. To generate the images on adisplay, a computer processing system may be used. Such displays mayoccupy a wearers entire field of view, or only occupy part of wearer'sfield of view. Further, head-mounted displays may vary in size, taking asmaller form such as a glasses-style display or a larger form such as ahelmet, for example.

Referring to FIG. 6, a computing system 600 of a VR device can include aprocessing system 602, storage system 604 (storing software 605,including instructions for processes 300, 330, 400, 420, 440, and 460),display subsystem 606, input subsystem 608, communication subsystem 610,and network interface and subsystem 612. Depending on implementation,more or fewer of these systems may be included. Referring to FIGS.7A-7C, a head-mounted display (HMD) can be worn by a user and cangenerate graphics, such as a view of a virtual space, in a displayportion of the HMD. The graphics presented on a head-mounted display cancover a large portion or even all of a user s field of view, providingan immersive experience to the user.

As shown in FIG. 7A, the example head-mounted display-based VR devicecan take the form of an HMD device 700. The illustrated HMD device 700implements computing system 600 in the form of wearable glasses orgoggles, but it will be appreciated that other forms are possible. TheHMD device 700 includes a see-through display subsystem 606 (e.g., an atleast partially see-through stereoscopic display) with one or morelenses 701 that may be configured to visually augment an appearance of aphysical environment being viewed by the user through the see-throughdisplay subsystem such that images may be displayed using lenses 701(e.g. using projection onto lenses 701, one or more waveguide systemsincorporated into the lenses 701, and/or in any other suitable manner).

In some examples, the see-through display subsystem may include one ormore regions that are transparent (e.g., optically clear) and mayinclude one or more regions that are opaque or semi-transparent. Inother examples, the see-through display subsystem may be transparent(e.g., optically clear) across an entire usable display surface of thesee-through display subsystem.

The HMD device 700 includes an optical sensor system 702 that mayinclude one or more optical sensors. In one example, the optical sensorsystem 702 can include one or more outward facing optical sensors thatmay be configured to acquire and detect the real-world background and/orphysical space from a similar vantage point (e.g., line of sight) asobserved by the user through the lenses 701. The optical sensor system702 may include a variety of sensors, such as one or both of a depthcamera/sensor and an RGB camera/sensor. In some cases, a high definitioncamera or other resolutions for image sensing may be used.

The sensors included with the HMD device 700 can support variousfunctionalities including head tracking to determine the 3D(three-dimensional) position and orientation of the user's head withinthe physical real-world space; and gaze tracking to ascertain adirection of the user's gaze.

For example, the HMD device 700 can include a position sensor system 703that may include one or more position sensors 704 such asaccelerometer(s), gyroscope(s), magnetometer(s), global positioningsystem(s) (GPS) 705, multilateration tracker(s) (not shown), and/orother sensors that output position sensor information useable as aposition, orientation, and/or movement of the relevant sensor.

When position sensor system 703 includes one or more motion sensors 704(e.g., inertial, multi-axis gyroscopic or acceleration sensors),movement and position/orientation/pose of a user's head may be detectedwhen the user is wearing the system.

The HMD device 700 may further include a gaze detection subsystem 706configured for detecting a direction of gaze of each eye of a user or adirection or location of focus. Gaze detection subsystem 706 may beconfigured to determine gaze directions of each of a user's eyes in anysuitable manner. For example, in the illustrative example shown, a gazedetection subsystem 706 includes one or more glint sources 707, such asinfrared light sources, that are configured to cause a glint of light toreflect from each eyeball of a user, and one or more image sensors 708,such as inward-facing sensors, that are configured to capture an imageof each eyeball of the user. Changes in the glints from the user'seyeballs and/or a location of a user's pupil, as determined from imagedata gathered using the image sensor(s) 708, may be used to determine adirection of gaze.

In addition, a location at which gaze lines projected from the user'seyes intersect the external display may be used to determine an objectat which the user is gazing (e.g. a displayed virtual object and/or realbackground object). Gaze detection subsystem 706 may have any suitablenumber and arrangement of light sources and image sensors. In someimplementations, the gaze detection subsystem 706 may be omitted.

The HMD device 700 may include one or more microphones 709 configured todetect sounds, such as voice commands from a user.

Position sensor system 703 (including motion sensors 704), as well asmicrophone(s) 705 and gaze detection subsystem 706, also may be employedas user input devices, such that a user may interact with the HMD device700 via gestures of the eye, neck and/or head, as well as via verbalcommands in some cases. These systems are represented as input subsystem608 in FIG. 6.

The HMD device 700 can be configured with one or more audio transducers710 (e.g., speakers, earphones, etc.) so that audio can be utilized aspart of the user experience.

The HMD device 700 can further include a controller 711, which includescomponents described with respect to computing system 600, such asprocessing system 602 and storage system 604. Controller 711 can be incommunication with the sensors 702, gaze detection subsystem 706, lenses701, and/or other components through, for example, a communicationssubsystem 610. The communications subsystem 610 can operate with anetwork interface and subsystem 612 to facilitate the display systembeing operated in conjunction with remotely located resources, such asprocessing, storage, power, data, and services. That is, in someimplementations, an HMD device can be operated as part of a system thatcan distribute resources and capabilities among different components andsubsystems.

The HMD device 700 may include instructions stored on the storage system604 for image production that direct the HMD device 700 to displayvirtual objects to the user, which are visually superimposed onto thephysical environment so as to be perceived at various depths andlocations. The HMD device 700 may use stereoscopy to visually place avirtual object at a desired depth by displaying separate images of thevirtual object to both of the user's eyes. To achieve the perception ofdepth, the instructions for image product may render the two images ofthe virtual object at a rendering focal plane of the HMD device 700,such that there is a binocular disparity between the relative positionsof the virtual object in the two images. For example, this binoculardisparity may be a horizontal disparity where the relative positions ofthe virtual object in the two images is separated by a distance in the xaxis direction. Here, the x axis may be defined as the axis extending tothe left and the right relative to the user, the y axis extending upwardand downward relative to the user, and the z axis extending forward andbackward relative to the user.

The horizontal disparity between the relative positions of the virtualobject in the two images will cause the user to perceive that thevirtual object is located at a certain depth within the viewed physicalenvironment due to stereopsis. Using this stereoscopy technique, the HMDdevice 700 may control the displayed images of the virtual objects, suchthat the user will perceive that the virtual objects exist at a desireddepth and location in the viewed physical environment.

Optical sensor information received from the optical sensor system 702and/or position sensor information received from position sensor system703 may be used to assess a position and orientation of the vantagepoint of the at least partially see-through stereoscopic displayrelative to other environmental objects. In some embodiments, theposition and orientation of the vantage point may be characterized withsix degrees of freedom (e.g., world-space X, Y, Z, pitch, roll, andyaw). The vantage point may be characterized globally or independent ofthe real-world background. The position and/or orientation may bedetermined with an on-board computing system (e.g., controller 711)and/or an off-board computing system.

Furthermore, the optical sensor information and the position sensorinformation may be used by a computing system to perform analysis of thereal-world background, such as depth analysis, surface reconstruction,environmental color and lighting analysis, or other suitable operations.In particular, the optical and positional sensor information may be usedto create a virtual model of the real-world background. In someembodiments, the position and orientation of the vantage point may becharacterized relative to this virtual space. Moreover, the virtualmodel may be used to determine positions of virtual objects in thevirtual space and add additional virtual objects to be displayed to theuser at a desired depth and location within the virtual world.

When the position sensor system 703 includes GPS 705, the system can usethe GPS 705 to determine a location of the HMD device 700. This may helpto identify real world objects, such as buildings, etc. that may belocated in the user's adjoining physical environment.

A power management subsystem (not shown) may include one or morebatteries and/or protection circuit modules (PCMs) and an associatedcharger interface and/or remote power interface for supplying power tocomponents in the HMD device 700.

It may be understood that sensors illustrated in, and described withrespect to, FIG. 7A are included for the purpose of example and are notintended to be limiting in any manner, as any other suitable sensorsand/or combination of sensors may be utilized to meet the needs of aparticular implementation of a head-mounted VR device. For example,biometric sensors (e.g., for detecting heart and respiration rates,blood pressure, brain activity, body temperature, etc.) or environmentalsensors (e.g., for detecting temperature, humidity, elevation, UV(ultraviolet) light levels, etc.) may be utilized in someimplementations.

FIGS. 7B and 7C illustrate additional configurations of a VR device.Referring to FIG. 7B, a VR device 720 may provide an immersiveexperience and be in the form of a mask. Referring to FIG. 7C, a VRdevice 730 can include a slot or holder for receiving a smartphone; andinclude clips or other means for securing the smartphone to the headset.The VR device can include straps or other structure to secure or attachthe VR device to a user's head. The screen of the smartphone would thusbe viewable to the user much in the same way as a conventional HMD hasan integrated screen. The smartphone can be leveraged to support the VRapplications and provide any of the computing elements described withrespect to FIG. 6.

It is to be understood that the VR devices may include additional and/oralternative sensors, cameras, microphones, input devices, outputdevices, etc. than those shown without departing from the scope of thepresent arrangement. Additionally, the physical configuration of adisplay device and its various sensors and subcomponents may take avariety of different forms without departing from the scope of thepresent arrangement.

As mentioned above, computing system 600 can implement a VR device,including, but not limited to HMD device 700 and devices 720 and 730.Computing system 600 includes a processing system 602, which can includea logic processor (and may even include multiple processors of same ordifferent types), and a storage system 604, which can include volatileand non-volatile memory.

Processing system 602 may include one or more physical processors(hardware) configured to execute software instructions. Additionally oralternatively, the logic processor may include one or more hardwarelogic circuits or firmware devices configured to executehardware-implemented logic or firmware instructions. Processors of theprocessing system 602 may be single-core or multi-core, and theinstructions executed thereon may be configured for sequential,parallel, and/or distributed processing. Individual components of theprocessing system 602 optionally may be distributed among two or moreseparate devices, which may be remotely located and/or configured forcoordinated processing. Aspects of the processing system 602 may bevirtualized and executed by remotely accessible, networked computingdevices configured in a cloud-computing configuration. In such a case,these virtualized aspects are run on different physical logic processorsof various different machines, it will be understood.

Processing system 602 includes one or more physical devices configuredto execute instructions. The processing system 602 may be configured toexecute instructions that are part of one or more applications,programs, routines, libraries, objects, components, data structures, orother logical constructs. Such instructions may be implemented toperform a task, implement a data type, transform the state of one ormore components, achieve a technical effect, or otherwise arrive at adesired result. When the instructions are software based (as opposed tohardware-based such as implemented in a field programmable gate array(FPGA) or digital logic), the instructions can be stored as software 605in the storage system 604.

Storage system 604 may include physical devices that are removableand/or built-in. Storage system 604 can include one or more volatile andnon-volatile storage devices such as optical memory (e.g., CD, DVD,HD-DVD, Blu-Ray Disc, etc.), semiconductor memory (e.g., RAM, SRAM,DRAM, ROM, EPROM, EEPROM, FLASH memory, etc.), and/or magnetic memory(e.g., hard-disk drive, floppy-disk drive, tape drive, MRAM, etc.), orother mass storage device technology. Storage system 604 may includedynamic, static, read/write, read-only, random-access,sequential-access, location-addressable, file-addressable, and/orcontent-addressable devices. It should be understood that a storagedevice or a storage medium of the storage system includes one or morephysical devices and excludes propagating signals per se.

Aspects of processing system 602 and storage system 604 may beintegrated together into one or more hardware-logic components. Suchhardware-logic components may include field-programmable gate arrays(FPGAs), program- and application-specific integrated circuits(PASIC/ASICs), program- and application-specific standard products(PSSP/ASSPs), system-on-a-chip (SOC), and complex programmable logicdevices (CPLDs), for example.

When included, display subsystem 606 may be used to present a visualrepresentation of data held by storage system 604. This visualrepresentation may take the form of a graphical user interface (GUI). Asthe herein described methods and processes change the data held by thestorage system, and thus transform the state of the storage system, thestate of display subsystem 606 may likewise be transformed to visuallyrepresent changes in the underlying data. Display subsystem 606 mayinclude one or more display devices utilizing virtually any type oftechnology. Such display devices may be combined with processing system602 and/or storage system 604 in a shared enclosure, or such displaydevices may be peripheral display devices. The at least partiallysee-through display of HMD 500 described above is one example of adisplay subsystem 606.

When included, input subsystem 608 may comprise or interface withselected natural user input (NUI) componentry. Such componentry may beintegrated or peripheral, and the transduction and/or processing ofinput actions may be handled on- or off-board. Example NUI componentrymay include a microphone for speech and/or voice recognition; aninfrared, color, stereoscopic, and/or depth camera for machine visionand/or gesture recognition; a head tracker, eye tracker, accelerometer,and/or gyroscope for motion detection and/or intent recognition; as wellas electric-field sensing componentry for assessing brain activity; anyof the sensors described above with respect to FIG. 7A and/or any othersuitable sensor.

When included, network interface and subsystem 612 may be configured tocommunicatively couple computing system 600 with one or more othercomputing devices. Network interface and subsystem 612 may include wiredand/or wireless communication devices compatible with one or moredifferent communication protocols. As non-limiting examples, the networkinterface and subsystem 612 may be configured for communication via awireless telephone network, or a wired or wireless, near-field, local-or wide-area network. In some embodiments, the network interface andsubsystem 612 may allow computing system 600 to send and/or receivemessages to and/or from other devices via a network such as theInternet.

Although the subject matter has been described in language specific tostructural features and/or acts, it is to be understood that the subjectmatter defined in the appended claims is not necessarily limited to thespecific features or acts described above. Rather, the specific featuresand acts described above are disclosed as examples of implementing theclaims and other equivalent features and acts are intended to be withinthe scope of the claims.

What is claimed is:
 1. One or more computer readable storage mediahaving instructions stored thereon that when executed by a processor ofa virtual reality device, direct the processor to: display a currentmode view in a view frame of the virtual reality device, the currentmode view comprising a current mode rule for a container space, whereinthe container space comprises an application container of anapplication; receive an overview command trigger; determine contextincluding a current container level; when the current container levelcan expand at least one level, expand to a next mode view, wherein thenext mode view is a next expanded container level; and apply a next moderule for the container space; receive a focus command trigger; and inresponse to the focus command trigger identify a region of interest inthe next mode view; adjust the view frame to the region of interest;display a focused mode view; and apply a focused mode rule for thecontainer space.
 2. The media of claim 1, wherein the current containerlevel comprises one of an application container level, a task level, andan overview level.
 3. The media of claim 2, wherein the currentcontainer level is the application container level, wherein the currentmode view comprises an application container space, wherein the currentmode rule for the container space comprises: operating the applicationwithin the application container space and stopping operation of anyapplications in spaces not in the view frame determined based on headmotion.
 4. The media of claim 3, wherein the application container spacecomprises one or more application container elements in the view frame.5. The media of claim 2, wherein the current container level is the tasklevel, wherein the current mode view comprises a task level spacecomprising at least two application container spaces, wherein each ofthe at least two application container spaces comprises one or moreapplication container elements in the view frame and has a correspondingapplication operating therein.
 6. The media of claim 5, wherein thecurrent mode rule for the container space comprises: operating thecorresponding application within each of the at least two applicationcontainer spaces and stopping operation of any applications in spacesnot in the view frame determined based on head motion.
 7. The media ofclaim 2, wherein the current container level is the overview level,wherein the current mode view comprises an overview space, the overviewspace providing a view of all application container spaces in the viewarea, wherein the current mode rule for the overview space comprises:reducing or stopping operation of any applications within theapplication container spaces.
 8. The media of claim 7, wherein thecurrent mode rule for the overview space further replaces content ineach application container space with a representation image.
 9. Themedia of claim 1, wherein the instructions to identify the region ofinterest direct the processor to: monitor head motion to identify aregion of interest based on position of head; and provide a signal toindicate to a user the identified region of interest.
 10. The media ofclaim 1, further comprising instructions to: in response to a head lockcommand, maintain the view frame regardless of head position of theuser; and in response to a world lock command, maintain the containerspace within the view frame while permitting head motion tracking withinthe container space.
 11. A method comprising: executing, via a virtualreality device, a plurality of applications; displaying, at anapplication container level, a current mode view in a view frame of thevirtual reality device, wherein the current mode view comprises acontainer space of one of the plurality of applications and anapplication container level rule for the container space; receiving anoverview command trigger; in response to receiving the overview commandtrigger, determining context, including that the current mode view is atthe application container level; and expanding to a next level view; anddisplaying, at a next level, the next level view in the view frame ofthe virtual reality device.
 12. The method of claim 11, wherein theapplication container level rule comprises: operating the applicationwithin the application container space and stopping operation of anyapplications in spaces not in the view frame determined based on headmotion.
 13. The method of claim 11, wherein the next level view is atask level view comprising: the container space of the one of theplurality of applications and a second container space of a second ofthe plurality of applications; and a task level rule, wherein the tasklevel rule comprises operating the one of the plurality of applicationswithin the container space, operating the second of the plurality ofapplications within the second container space, and stopping operationof any applications in spaces not in the view frame determined based onhead motion.
 14. The method of claim 11, wherein the next level view isan overview level view comprising: an overview space, the overview spaceproviding a view of all application container spaces in the view area;and an overview level rule, wherein the overview level rule comprisesreducing or stopping operation of any of the plurality of applications.15. The method of claim 14, further comprising: receiving a focuscommand trigger; in response to receiving the focus command trigger,identifying a region of interest; and adjusting the view frame to theregion of interest; and displaying, at a prior level, a prior level viewwith respect to the region of interest in the view frame of the virtualreality device.
 16. The method of claim 15, wherein the prior level viewis a task level view comprising: the container space of the one of theplurality of applications and a second container space of a second ofthe plurality of applications; and a task level rule, wherein the tasklevel rule comprises operating the one of the plurality of applicationswithin the container space, operating the second of the plurality ofapplications within the second container space, and stopping operationof any applications in spaces not in the view frame determined based onhead motion.
 17. The method of claim 15, wherein the prior level view isan application container level view, wherein the application containerlevel view comprises: a container space of one of the plurality ofapplications corresponding to the region of interest; and theapplication container level rule for the container space, wherein theapplication container level rule comprises: operating the applicationwithin the application container space and stopping operation of anyapplications in spaces not in the view frame determined based on headmotion.
 18. A virtual reality device, comprising: a processor;head-tracking sensors; one or more computer-readable storage media;instructions for a container space feature stored on the one or morecomputer-readable storage media that, when executed by the processor,direct the processor to at least: receive an overview command trigger;determine context including a current container level; when the currentcontainer level can expand at least one level, expand to a next modeview, wherein the next mode view is a next expanded container level; andapply a next mode rule for the container space; receive a focus commandtrigger; and in response to the focus command trigger identify a regionof interest in the next mode view; adjust the view frame to the regionof interest; display a focused mode view; and apply a focused mode rulefor the container space.
 19. The virtual reality device of claim 18,wherein the instructions that identify the region of interest in thenext mode view direct the processor to: determine, using thehead-tracking sensors, a head position with respect to an applicationcontainer.
 20. The virtual reality device of claim 18, wherein theinstructions to identify the region of interest direct the processor to:monitor head motion to identify a region of interest based on positionof head; and provide a signal to indicate to a user the identifiedregion of interest.